Method and apparatus for removing a serving cell in a wireless communication system

ABSTRACT

A method and apparatus are disclosed for removing a serving cell in a wireless communication system. The method includes a UE is served by a first cell controlled by a first eNB. The method also includes the UE is configured with a second cell controlled by a second eNB. The method further includes the UE is configured with a radio bearer, wherein there is a PDCP entity corresponding to the RB and there are two RLC entities corresponding to the RB, one RLC entity for data transfer via the first cell and the other RLC entity for data transfer via the second cell. In addition, the method includes the UE delivers out-of-sequence RLC SDUs reassembled by the RLC entity corresponding to the first cell to the PDCP entity in response to reception of an instruction to remove the second cell. In one embodiment, the method also includes the UE transmits a PDCP status report to the first eNB to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB.

CROSS-REFERENCE TO RELATED APPLICATIONS

The present application claims the benefit of U.S. Provisional Patent Application Ser. No. 61/807,103 filed on Apr. 1, 2013, the entire disclosure of which is incorporated herein by reference.

FIELD

This disclosure generally relates to wireless communication networks, and more particularly, to a method and apparatus for removing a serving cell in a wireless communication system.

BACKGROUND

With the rapid rise in demand for communication of large amounts of data to and from mobile communication devices, traditional mobile voice communication networks are evolving into networks that communicate with Internet Protocol (IP) data packets. Such IP data packet communication can provide users of mobile communication devices with voice over IP, multimedia, multicast and on-demand communication services.

An exemplary network structure for which standardization is currently taking place is an Evolved Universal Terrestrial Radio Access Network (E-UTRAN). The E-UTRAN system can provide high data throughput in order to realize the above-noted voice over IP and multimedia services. The E-UTRAN system's standardization work is currently being performed by the 3GPP standards organization. Accordingly, changes to the current body of 3GPP standard are currently being submitted and considered to evolve and finalize the 3GPP standard.

SUMMARY

A method and apparatus are disclosed for removing a serving cell in a wireless communication system. The method includes a UE (User Equipment) is served by a first cell controlled by a first eNB (evolved Node B). The method also includes the UE is configured with a second cell controlled by a second eNB. The method further includes the UE is configured with a radio bearer (RB), wherein there is a PDCP (Packet Data Convergence Protocol) entity corresponding to the RB and there are two RLC (Radio Link Control) entities corresponding to the RB, one RLC entity for data transfer via the first cell and the other RLC entity for data transfer via the second cell. In addition, the method includes the UE delivers out-of-sequence RLC SDUs (Service Data Units) reassembled by the RLC entity corresponding to the first cell to the PDCP entity in response to reception of an instruction to remove the second cell. In one embodiment, the method also includes the UE transmits a PDCP status report to the first eNB to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 shows a diagram of a wireless communication system according to one exemplary embodiment.

FIG. 2 is a block diagram of a transmitter system (also known as access network) and a receiver system (also known as user equipment or UE) according to one exemplary embodiment.

FIG. 3 is a functional block diagram of a communication system according to one exemplary embodiment.

FIG. 4 is a functional block diagram of the program code of FIG. 3 according to one exemplary embodiment.

FIG. 5 illustrates a prior art protocol architecture according to one exemplary embodiment.

FIG. 6 illustrates an exemplary prior art PDCP status report according to one exemplary embodiment.

FIG. 7 illustrates a flow chart according to one exemplary embodiment.

FIG. 8 illustrates a flow chart according to one exemplary embodiment.

FIG. 9 illustrates a flow chart according to one exemplary embodiment.

DETAILED DESCRIPTION

The exemplary wireless communication systems and devices described below employ a wireless communication system, supporting a broadcast service. Wireless communication systems are widely deployed to provide various types of communication such as voice, data, and so on. These systems may be based on code division multiple access (CDMA), time division multiple access (TDMA), orthogonal frequency division multiple access (OFDMA), 3GPP LTE (Long Term Evolution) wireless access, 3GPP LTE-A or LTE-Advanced (Long Term Evolution Advanced), 3GPP2 UMB (Ultra Mobile Broadband), WiMax, or some other modulation techniques.

In particular, the exemplary wireless communication systems devices described below may be designed to support one or more standards such as the standard offered by a consortium named “3rd Generation Partnership Project” referred to herein as 3GPP, including Document Nos. 3GPP TR36.392 v12.0.0 (2012-12), “Scenarios and Requirements for Small Cell Enhancements for E-UTRA and E-UTRAN”; RP-122033, “New Study Item Description: Small Cell enhancements for E-UTRA and E-UTRAN—Higher-layer aspects”; TS 36.300 V11.4.0 (2012-12), “E-UTRAN; Overall description; Stage 2”; TS 36.331 V11.3.0 (2013-03), “E-UTRA; RRC protocol specification”; R2-130420, “Protocol architecture alternatives for dual connectivity”; and R2-130570, “Scenarios and benefits of dual connectivity”. The standards and documents listed above are hereby expressly incorporated herein.

FIG. 1 shows a multiple access wireless communication system according to one embodiment of the invention. An access network 100 (AN) includes multiple antenna groups, one including 104 and 106, another including 108 and 110, and an additional including 112 and 114. In FIG. 1, only two antennas are shown for each antenna group, however, more or fewer antennas may be utilized for each antenna group. Access terminal 116 (AT) is in communication with antennas 112 and 114, where antennas 112 and 114 transmit information to access terminal 116 over forward link 120 and receive information from access terminal 116 over reverse link 118. Access terminal (AT) 122 is in communication with antennas 106 and 108, where antennas 106 and 108 transmit information to access terminal (AT) 122 over forward link 126 and receive information from access terminal (AT) 122 over reverse link 124. In a FDD system, communication links 118, 120, 124 and 126 may use different frequency for communication. For example, forward link 120 may use a different frequency then that used by reverse link 118.

Each group of antennas and/or the area in which they are designed to communicate is often referred to as a sector of the access network. In the embodiment, antenna groups each are designed to communicate to access terminals in a sector of the areas covered by access network 100.

In communication over forward links 120 and 126, the transmitting antennas of access network 100 may utilize beamforming in order to improve the signal-to-noise ratio of forward links for the different access terminals 116 and 122. Also, an access network using beamforming to transmit to access terminals scattered randomly through its coverage causes less interference to access terminals in neighboring cells than an access network transmitting through a single antenna to all its access terminals.

An access network (AN) may be a fixed station or base station used for communicating with the terminals and may also be referred to as an access point, a Node B, a base station, an enhanced base station, an eNodeB, or some other terminology. An access terminal (AT) may also be called user equipment (UE), a wireless communication device, terminal, access terminal or some other terminology.

FIG. 2 is a simplified block diagram of an embodiment of a transmitter system 210 (also known as the access network) and a receiver system 250 (also known as access terminal (AT) or user equipment (UE)) in a MIMO system 200. At the transmitter system 210, traffic data for a number of data streams is provided from a data source 212 to a transmit (TX) data processor 214.

In one embodiment, each data stream is transmitted over a respective transmit antenna. TX data processor 214 formats, codes, and interleaves the traffic data for each data stream based on a particular coding scheme selected for that data stream to provide coded data.

The coded data for each data stream may be multiplexed with pilot data using OFDM techniques. The pilot data is typically a known data pattern that is processed in a known manner and may be used at the receiver system to estimate the channel response. The multiplexed pilot and coded data for each data stream is then modulated (i.e., symbol mapped) based on a particular modulation scheme (e.g., BPSK, QPSK, M-PSK, or M-QAM) selected for that data stream to provide modulation symbols. The data rate, coding, and modulation for each data stream may be determined by instructions performed by processor 230.

The modulation symbols for all data streams are then provided to a TX MIMO processor 220, which may further process the modulation symbols (e.g., for OFDM). TX MIMO processor 220 then provides N_(T) modulation symbol streams to N_(T) transmitters (TMTR) 222 a through 222 t. In certain embodiments, TX MIMO processor 220 applies beamforming weights to the symbols of the data streams and to the antenna from which the symbol is being transmitted.

Each transmitter 222 receives and processes a respective symbol stream to provide one or more analog signals, and further conditions (e.g., amplifies, filters, and upconverts) the analog signals to provide a modulated signal suitable for transmission over the MIMO channel. N_(T) modulated signals from transmitters 222 a through 222 t are then transmitted from N_(T) antennas 224 a through 224 t, respectively.

At receiver system 250, the transmitted modulated signals are received by N_(R) antennas 252 a through 252 r and the received signal from each antenna 252 is provided to a respective receiver (RCVR) 254 a through 254 r. Each receiver 254 conditions (e.g., filters, amplifies, and downconverts) a respective received signal, digitizes the conditioned signal to provide samples, and further processes the samples to provide a corresponding “received” symbol stream.

An RX data processor 260 then receives and processes the N_(R) received symbol streams from N_(R) receivers 254 based on a particular receiver processing technique to provide N_(T) “detected” symbol streams. The RX data processor 260 then demodulates, deinterleaves, and decodes each detected symbol stream to recover the traffic data for the data stream. The processing by RX data processor 260 is complementary to that performed by TX MIMO processor 220 and TX data processor 214 at transmitter system 210.

A processor 270 periodically determines which pre-coding matrix to use (discussed below). Processor 270 formulates a reverse link message comprising a matrix index portion and a rank value portion.

The reverse link message may comprise various types of information regarding the communication link and/or the received data stream. The reverse link message is then processed by a TX data processor 238, which also receives traffic data for a number of data streams from a data source 236, modulated by a modulator 280, conditioned by transmitters 254 a through 254 r, and transmitted back to transmitter system 210.

At transmitter system 210, the modulated signals from receiver system 250 are received by antennas 224, conditioned by receivers 222, demodulated by a demodulator 240, and processed by a RX data processor 242 to extract the reserve link message transmitted by the receiver system 250. Processor 230 then determines which pre-coding matrix to use for determining the beamforming weights then processes the extracted message.

Turning to FIG. 3, this figure shows an alternative simplified functional block diagram of a communication device according to one embodiment of the invention. As shown in FIG. 3, the communication device 300 in a wireless communication system can be utilized for realizing the UEs (or ATs) 116 and 122 in FIG. 1, and the wireless communications system is preferably the LTE system. The communication device 300 may include an input device 302, an output device 304, a control circuit 306, a central processing unit (CPU) 308, a memory 310, a program code 312, and a transceiver 314. The control circuit 306 executes the program code 312 in the memory 310 through the CPU 308, thereby controlling an operation of the communications device 300. The communications device 300 can receive signals input by a user through the input device 302, such as a keyboard or keypad, and can output images and sounds through the output device 304, such as a monitor or speakers. The transceiver 314 is used to receive and transmit wireless signals, delivering received signals to the control circuit 306, and outputting signals generated by the control circuit 306 wirelessly.

FIG. 4 is a simplified block diagram of the program code 312 shown in FIG. 3 in accordance with one embodiment of the invention. In this embodiment, the program code 312 includes an application layer 400, a Layer 3 portion 402, and a Layer 2 portion 404, and is coupled to a Layer 1 portion 406. The Layer 3 portion 402 generally performs radio resource control. The Layer 2 portion 404 generally performs link control. The Layer 1 portion 406 generally performs physical connections.

3GPP TR 36.392 v12.0.0 states:

Small cells using low power nodes are considered promising to cope with mobile traffic explosion, especially for hotspot deployments in indoor and outdoor scenarios. A low-power node generally means a node whose Tx power is lower than macro node and BS classes, for example Pico and Femto eNB are both applicable. Small cell enhancements for E-UTRA and E-UTRAN will focus on additional functionalities for enhanced performance in hotspot areas for indoor and outdoor using low power nodes. This document captures the scenarios and requirements for small cell enhancements. 3GPP TR 36.913 [3] should be used as reference whenever applicable in order to avoid duplication of the requirements.

In addition, 3GPP RP-122033 states:

4 Objective *

The objective of this study is to identify potential technologies in the protocol and architecture for enhanced support of small cell deployment and operation which should satisfy scenarios and requirements defined in TR 36.932. The study shall be conducted on the following aspects:

-   -   Identify and evaluate the benefits of UEs having dual         connectivity to macro and small cell layers served by different         or same carrier and for which scenarios such dual connectivity         is feasible and beneficial.     -   Identify and evaluate potential architecture and protocol         enhancements for the scenarios in TR 36.932 and in particular         for the feasible scenario of dual connectivity and minimize core         network impacts if feasible, including:         -   Overall structure of control and user plane and their             relation to each other, e.g., supporting C-plane and U-plane             in different nodes, termination of different protocol             layers, etc.     -   Identify and evaluate the necessity of overall Radio Resource         Management structure and mobility enhancements for small cell         deployments:         -   Mobility mechanisms for minimizing inter-node UE context             transfer and signalling towards the core network.         -   Measurement and cell identification enhancements while             minimizing increased UE battery consumption.             For each potential enhancement, the gain, complexity and             specification impact should be assessed.             The study shall focus on potential enhancements which are             not covered by other SI/WIs.

Furthermore, 3GPP TS 36.300 V11.4.0 provides the following the description regarding Carrier Aggregation (CA):

5.5 Carrier Aggregation

In Carrier Aggregation (CA), two or more Component Carriers (CCs) are aggregated in order to support wider transmission bandwidths up to 100 MHz. A UE may simultaneously receive or transmit on one or multiple CCs depending on its capabilities:

-   -   A UE with single timing advance capability for CA can         simultaneously receive and/or transmit on multiple CCs         corresponding to multiple serving cells sharing the same timing         advance (multiple serving cells grouped in one TAG);     -   A UE with multiple timing advance capability for CA can         simultaneously receive and/or transmit on multiple CCs         corresponding to multiple serving cells with different timing         advances (multiple serving cells grouped in multiple TAGs).         E-UTRAN ensures that each TAG contains at least one serving         cell;     -   A non-CA capable UE can receive on a single CC and transmit on a         single CC corresponding to one serving cell only (one serving         cell in one TAG).         CA is supported for both contiguous and non-contiguous CCs with         each CC limited to a maximum of 110 Resource Blocks in the         frequency domain using the Rel-8/9 numerology.         It is possible to configure a UE to aggregate a different number         of CCs originating from the same eNB and of possibly different         bandwidths in the UL and the DL:     -   The number of DL CCs that can be configured depends on the DL         aggregation capability of the UE;     -   The number of UL CCs that can be configured depends on the UL         aggregation capability of the UE;     -   It is not possible to configure a UE with more UL CCs than DL         CCs;     -   In typical TDD deployments, the number of CCs and the bandwidth         of each CC in UL and DL is the same.     -   The number of TAGs that can be configured depends on the TAG         capability of the UE.         CCs originating from the same eNB need not to provide the same         coverage.         CCs shall be LTE Rel-8/9 compatible. Nevertheless, existing         mechanisms (e.g. barring) may be used to avoid Rel-8/9 UEs to         camp on a CC.         The spacing between centre frequencies of contiguously         aggregated CCs shall be a multiple of 300 kHz. This is in order         to be compatible with the 100 kHz frequency raster of Rel-8/9         and at the same time preserve orthogonality of the subcarriers         with 15 kHz spacing. Depending on the aggregation scenario, the         n x 300 kHz spacing can be facilitated by insertion of a low         number of unused subcarriers between contiguous CCs.

7.5 Carrier Aggregation

When CA is configured, the UE only has one RRC connection with the network. At RRC connection establishment/re-establishment/handover, one serving cell provides the NAS mobility information (e.g. TAI), and at RRC connection re-establishment/handover, one serving cell provides the security input. This cell is referred to as the Primary Cell (PCell). In the downlink, the carrier corresponding to the PCell is the Downlink Primary Component Carrier (DL PCC) while in the uplink it is the Uplink Primary Component Carrier (UL PCC). Depending on UE capabilities, Secondary Cells (SCells) can be configured to form together with the PCell a set of serving cells. In the downlink, the carrier corresponding to an SCell is a Downlink Secondary Component Carrier (DL SCC) while in the uplink it is an Uplink Secondary Component Carrier (UL SCC). The configured set of serving cells for a UE therefore always consists of one PCell and one or more SCells:

-   -   For each SCell the usage of uplink resources by the UE in         addition to the downlink ones is configurable (the number of DL         SCCs configured is therefore always larger than or equal to the         number of UL SCCs and no SCell can be configured for usage of         uplink resources only);     -   From a UE viewpoint, each uplink resource only belongs to one         serving cell;     -   The number of serving cells that can be configured depends on         the aggregation capability of the UE (see subclause 5.5);     -   PCell can only be changed with handover procedure (i.e. with         security key change and RACH procedure);     -   PCell is used for transmission of PUCCH;     -   Unlike SCells, PCell cannot be de-activated (see subclause         11.2);     -   Re-establishment is triggered when PCell experiences RLF, not         when SCells experience RLF;     -   NAS information is taken from PCell.         The reconfiguration, addition and removal of SCells can be         performed by RRC. At intra-LTE handover, RRC can also add,         remove, or reconfigure SCells for usage with the target PCell.         When adding a new SCell, dedicated RRC signalling is used for         sending all required system information of the SCell i.e. while         in connected mode, UEs need not acquire broadcasted system         information directly from the SCells.

Also, 3GPP TS 36.331 V11.3.0 provides the following description:

5.3.5.4 Reception of an RRCConnectionReconfiguration including the mobilityControlInfo by the UE (handover) If the RRCConnectionReconfiguration message includes the mobilityControlInfo and the UE is able to comply with the configuration included in this message, the UE shall:

-   -   1> stop timer T310, if running;     -   1> start timer T304 with the timer value set to t304, as         included in the mobilityControlInfo;     -   1> if the carrierFreq is included:         -   2> consider the target PCell to be one on the frequency             indicated by the carrierFreq with a physical cell identity             indicated by the targetPhysCelld;     -   1> else:         -   2> consider the target PCell to be one on the frequency of             the source PCell with a physical cell identity indicated by             the targetPhysCelld;     -   1> start synchronising to the DL of the target PCell;     -   NOTE 1: The UE should perform the handover as soon as possible         following the reception of the RRC message triggering the         handover, which could be before confirming successful reception         (HARQ and ARQ) of this message.     -   1> reset MAC;     -   1> re-establish PDCP for all RBs that are established;     -   NOTE 2: The handling of the radio bearers after the successful         completion of the PDCP re-establishment, e.g. the         re-transmission of unacknowledged PDCP SDUs (as well as the         associated status reporting), the handling of the SN and the         HFN, is specified in TS 36.323 [8].     -   1> re-establish RLC for all RBs that are established;     -   1> configure lower layers to consider the SCell(s), if         configured, to be in deactivated state;     -   1> apply the value of the newUE-Identity as the C-RNTI;     -   1> if the RRCConnectionReconfiguration message includes the         fullConfig:         -   2> perform the radio configuration procedure as specified in             section 5.3.5.8;     -   1> configure lower layers in accordance with the received         radioResourceConfigCommon;     -   1> configure lower layers in accordance with any additional         fields, not covered in the previous, if included in the received         mobilityControlInfo;     -   1> if the RRCConnectionReconfiguration message includes the         radioResourceConfigDedicated:         -   2> perform the radio resource configuration procedure as             specified in 5.3.10;     -   1> if the keyChangeIndicator received in the securityConfigHO is         set to TRUE:         -   2> update the K_(eNB) key based on the fresh K_(ASME) key             taken into use with the previous successful NAS SMC             procedure, as specified in TS 33.401 [32];     -   1> else:         -   2> update the K_(eNB) key based on the current K_(eNB) or             the NH, using the nextHopChainingCount value indicated in             the securityConfigHO, as specified in TS 33.401 [32];     -   1> store the nextHopChainingCount value;     -   1> if the securityAlgorithmConfig is included in the         securityConfigHO:         -   2> derive the K_(RRCint) key associated with the             integrityProtAlgorithm, as specified in TS 33.401 [32];         -   2> if connected as an RN:             -   3> derive the K_(UPint) key associated with the                 integrityProtAlgorithm, as specified in TS 33.401 [32];         -   2> derive the K_(RRCenc) key and the K_(UPenc) key             associated with the cipheringAlgorithm, as specified in TS             33.401 [32];     -   1> else:         -   2> derive the K_(RRCint) key associated with the current             integrity algorithm, as specified in TS 33.401 [32];         -   2> if connected as an RN:             -   3> derive the K_(UPint) key associated with the current                 integrity algorithm, as specified in TS 33.401 [32];         -   2> derive the K_(RRCenc) key and the K_(UPenc) key             associated with the current ciphering algorithm, as             specified in TS 33.401 [32];     -   1> configure lower layers to apply the integrity protection         algorithm and the K_(RRCint) key, i.e. the integrity protection         configuration shall be applied to all subsequent messages         received and sent by the UE, including the message used to         indicate the successful completion of the procedure;     -   1> configure lower layers to apply the ciphering algorithm, the         K_(RRCenc) key and the K_(UPenc) key, i.e. the ciphering         configuration shall be applied to all subsequent messages         received and sent by the UE, including the message used to         indicate the successful completion of the procedure;     -   1> if connected as an RN:         -   2> configure lower layers to apply the integrity protection             algorithm and the K_(UPint) key, for current or subsequently             established DRBs that are configured to apply integrity             protection, if any;     -   1> if the received RRCConnectionReconfiguration includes the         sCellToReleaseList:         -   2> perform SCell release as specified in 5.3.10.3a;     -   1> if the received RRCConnectionReconfiguration includes the         sCellToAddModList:         -   2> perform SCell addition or modification as specified in             5.3.10.3b;     -   1> if the received RRCConnectionReconfiguration includes the         systemInformationBlockType1Dedicated:         -   2> perfom the actions upon reception of the             SystemInformationBlockType1 message as specified in 5.2.2.7;     -   1> perform the measurement related actions as specified in         5.5.6.1;     -   1> if the RRCConnectionReconfiguration message includes the         measConfig:         -   2> perform the measurement configuration procedure as             specified in 5.5.2;     -   1> perform the measurement identity autonomous removal as         specified in 5.5.2.2a;     -   1> release reportProximityConfig and clear any associated         proximity status reporting timer;     -   1> if the RRCConnectionReconfiguration message includes the         otherConfig:         -   2> perform the other configuration procedure as specified in             5.3.10.9;     -   1> set the content of RRCConnectionReconfigurationComplete         message as follows:         -   2> if the UE has radio link failure or handover failure             information available in VarRLF-Report and if the RPLMN is             included in plmn-IdentityList stored in VarRLF-Report:             -   3> include rlf-InfoAvailable;         -   2> if the UE has logged measurements available for E-UTRA             and if the RPLMN is included in plmn-IdentityList stored in             VarLogMeasReport:             -   3> include the logMeasAvailable;         -   2> if the UE has connection establishment failure             information available in VarConnEstFailReport and if the             RPLMN is equal to plmn-Identity stored in             VarConnEstFailReport:             -   3> include connEstFailInfoAvailable;     -   1> submit the RRCConnectionReconfigurationComplete message to         lower layers for transmission;     -   1> if MAC successfully completes the random access procedure:         -   2> stop timer T304;         -   2> apply the parts of the CQI reporting configuration, the             scheduling request configuration and the sounding RS             configuration that do not require the UE to know the SFN of             the target PCell, if any;         -   2> apply the parts of the measurement and the radio resource             configuration that require the UE to know the SFN of the             target PCell (e.g. measurement gaps, periodic CQI reporting,             scheduling request configuration, sounding RS             configuration), if any, upon acquiring the SFN of the target             PCell;     -   NOTE 3: Whenever the UE shall setup or reconfigure a         configuration in accordance with a field that is received it         applies the new configuration, except for the cases addressed by         the above statements.         -   2> if the UE is configured to provide IDC indications:             -   3> if the UE has transmitted an InDeviceCoexIndication                 message during the last 1 second preceding reception of                 the RRCConnectionReconfiguration message including                 mobilityControlInfo:                 -   4> initiate transmission of the                     InDeviceCoexIndication message in accordance with                     5.6.9.3;         -   2> if the UE is configured to provide power preference             indications:             -   3> if the UE has transmitted a UEAssistanceInformation                 message during the last 1 second preceding reception of                 the RRCConnectionReconfiguration message including                 mobilityControlInfo:                 -   4> initiate transmission of the                     UEAssistanceInformation message in accordance with                     5.6.10.3;         -   2> the procedure ends;     -   NOTE 4: The UE is not required to determine the SFN of the         target PCell by acquiring system information from that cell         before performing RACH access in the target PCell.

5.3.10.3b SCell Addition/Modification

The UE shall:

-   -   1> for each sCellIndex value included in the sCellToAddModList         that is not part of the current UE configuration (SCell         addition):         -   2> add the SCell, corresponding to the cellIdentification,             in accordance with the received             radioResourceConfigCommonSCell and             radioResourceConfigDedicatedSCell;         -   2> configure lower layers to consider the SCell to be in             deactivated state;     -   1> for each sCellIndex value included in the sCellToAddModList         that is part of the current UE configuration (SCell         modification):         -   2> modify the SCell configuration in accordance with the             received radioResourceConfigDedicatedSCell;

In general, 3GPP R2-130420 discusses protocol architecture alternatives for dual connectivity. Alternative U3 (discussed in 3GPP R2-130420) is a centralized PDCP (Packet Data Convergence Protocol) termination, while Alternative U4 (discussed in 3GPP R2-130420) is a distributed protocol termination for user plane. The pros and cons of alternatives U3 and U4 described in 3GPP R2-130420 as follows:

3.3 Alternative U3: Centralized PDCP termination

-   -   Pros:         -   No extra load on EPC in terms of number of connections and             path switches     -   Cons:         -   Requirements on backhaul between macro and low power node             -   High capacity             -   Medium/Loose latency (PDCP reordering)         -   User data need to pass through central point

3.4 Alternative U4: Distributed Protocol Termination

-   -   Pros:         -   Supports local breakout at the low power eNB. User plane can             be optimized towards EPC         -   Good support for non-ideal backhaul             -   No user data transmission required between macro and low                 power eNBs         -   Establishing/removing low power node connectivity and             PDCP/RLC relocation can be based on Rel-8 handover procedure             with PDCP forwarding.     -   Cons:         -   Extra load on EPC in terms of number of connections and path             switches         -   Possible security implications need further study

Furthermore, in general, 3GPP R2-130570 discusses scenarios and benefits of dual connectivity, and addresses several protocol architecture alternatives for dual connectivity.

In general, with the protocol architecture Alternative U3 (centralized PDCP termination) proposed in 3GPP R2-130420, there are three potential ways of DRB allocation for Radio Bearer 1 (RB1), Radio Bearer 2 (RB2), and Radio Bearer 3 (RB3), as shown in FIG. 5. In particular, as illustrated in FIG. 5, RB1 is allocated to the macro eNB; RB2 is allocated to both the macro eNB and the small cell eNB; and RB3 is allocated to the small eNB, except the PDCP entity.

The way that RB 1 is allocated could be applied to a real-time service to reduce transfer delay due to X2 interface. The ways that RB2 and RB3 are allocated could be applied to non-real-time services. In particular, the way that RB2 is allocated is generally more flexible and efficient in terms of resource usage between the macro cell and the small cell. For example, packet transfer could be scheduled based on the current traffic load of each cell. If the traffic load of a cell is light, more packet transfers could be scheduled on the cell for traffic load balancing. UE (and eNB) behavior for supporting the allocation of DRB (Data Radio Bearer) to both the macro cell and the small cell would need to be considered.

If a DRB is allocated to both the macro cell and the small cell, the macro eNB would distribute downlink PDCP packets (or PDUs) of a DRB to the corresponding RLC (Radio Link Control) entities in both the macro eNB and the small cell eNB. The small cell may be removed due to UE mobility or traffic load change in both cells. When the small cell is removed in the UE, the out-of-sequence AM mode RLC SDUs (Service Data Unites)—or PDCP PDUs (Packet Data Units)—reassembled by the RLC entity corresponding to the small cell eNB should be delivered to the PDCP entity. Otherwise, those RLC SDUs would be lost after the small cell is removed.

Furthermore, it would be beneficial for the UE to transmit a PDCP status report to the macro eNB to indicate which PDCP SDUs have been received and which PDCP SDUs need to be retransmitted (for example, due to missing or header decompression failure), if the PDCP status report is configured as required to the RB.

FIG. 6 shows an example of PDCP status report 600. As shown in FIG. 6, before the small cell is removed, the PDCP in the UE only receives PDCP PDUs 1, 2, 3, 4, 5, 6, 7, 8, and 9 from both RLC entities. When the small cell is removed, the RLC entity corresponding to the small cell delivers out-of-sequence PDCP PDUs (including PDUs 16, 17, 18, and 20) to the PDCP entity. Thus, the following PDCP PDUs are received in the PDCP entity: 1, 2, 3, 4, 5, 6, 7, 8, 9, 16, 17, 18, and 20. In this situation, the UE would transmit a PDCP status report to indicate PDUs 10, 11, 12, 13, 14, 15, and 19 are missing.

After receiving the PDCP status report, the PDCP in the macro eNB would retransmit PDUs 10, 11, 12, 13, 14, 15, and 19 if the macro eNB did not keep information about which PDCP PDUs were distributed to the small cell for transmissions, even though PDUs 12, 13, 14, and 15 have been received by the UE from the macro cell. However, retransmissions of these PDUs would not be needed, and would consume extra radio resources unnecessarily.

To solve the above problem, the macro eNB could store information about which PDCP packets (SDUs/PDUs) are distributed to the small cell or the macro cell for transmissions. Alternatively, a predefined rule (e.g., packets with odd SNs to the macro cell and packets with even SNs to the small cell) could be used for PDCP packet distribution between the macro cell and the small cell so that after receiving the PDCP status report from the UE, the macro eNB would know which PDCP packets should be retransmitted due to the removal of the small cell. In principle, only the PDCP packets delivered to the small cell would be considered as candidates for retransmission due to the removal of the small cell. In general, the former solution would require more memories; and the latter solution would impose additional limitations to PDCP packet distribution.

Another alternative would be for the UE to deliver to the PDCP entity the out-of-sequence AM mode RLC SDUs (or PDCP PDUs) reassembled by the RLC entity corresponding to the macro cell so that the PDCP entity in the UE could transmit a PDCP status report which would precisely indicate all PDCP packets to be retransmitted. Accordingly, when the small cell is removed, the macro eNB should also deliver to the PDCP entity out-of-sequence AM mode RLC SDUs (or PDCP PDUs) reassembled by the RLC entity corresponding to the macro cell.

FIG. 7 is a flow chart 700 from the perspective of a UE in accordance with one exemplary embodiment. In step 705, the UE is served by a first cell controlled by a first eNB. In step 710, the UE is configured with a second cell controlled by a second eNB. In step 715, the UE is configured with a RB, wherein there is a PDCP entity corresponding to the RB and there are two RLC entities corresponding to the RB, the first RLC entity is for data transfer via the first cell and the second RLC entity is for data transfer via the second cell. In step 720, the UE delivers out-of-sequence RLC SDUs reassembled by the RLC entity corresponding to the first cell to the PDCP entity in response to reception of an instruction to remove the second cell. In one embodiment, as shown in step 725, the UE transmits a PDCP status report to the first eNB to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB. In another embodiment, the UE could re-establish the RLC entity corresponding to the RB for the first cell, as shown in step 730.

In one embodiment, there could be two separate MAC (Medium Access Control) entities in the UE to support the first eNB and the second eNB. In addition, the RB could be used to transmit U-plane data. Furthermore, one or both of the RLC entities could be configured with an Acknowledged Mode (AM). In another embodiment, the PDCP packets could be PDCP SDUs and/or PDUs.

Referring back to FIGS. 3 and 4, in one embodiment, the device 300 could include a program code 312 stored in memory 310 for removing serving cells in a wireless communication system. In this embodiment, the device 300 operates in a scenario where (i) the UE is served by a first cell controlled by a first eNB, (ii) the UE is configured with a second cell controlled by a second eNB, and (iii) the UE is configured with a RB, wherein there is a PDCP entity corresponding to the RB and there are two RLC entities corresponding to the RB, the first RLC entity is for data transfer via the first cell and the second RLC entity is for data transfer via the second cell.

The CPU 308 could execute the program code 312 to enable the UE to deliver out-of-sequence RLC SDUs reassembled by the RLC entity corresponding to the first cell to the PDCP entity in response to reception of an instruction to remove the second cell. In one embodiment, the CPU 308 could execute the program code 312 to enable the UE to transmit a PDCP status report to the first eNB to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB. In another embodiment, the CPU 308 could execute the program code 312 to enable the UE to re-establish the RLC entity corresponding to the RB for the first cell. In addition, the CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.

FIG. 8 is a flow chart 800 from the perspective of a UE in accordance with one exemplary embodiment. In step 805, the UE is served by a first cell controlled by a first eNB. In step 810, the UE is configured with a second cell controlled by a second eNB. In step 815, the UE is configured with a RB, wherein there is a PDCP entity corresponding to the RB and there are two RLC entities corresponding to the RB, the first RLC entity is for data transfer via the first cell and the second RLC entity is for data transfer via the second cell. In step 820, the UE transmits a PDCP status report to the first eNB, in response to reception of an instruction to remove the second cell, to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB. In one embodiment, as shown in step 825, the UE delivers out-of-sequence RLC SDUs reassembled by the RLC entity corresponding to the first cell to the PDCP entity. In another embodiment, the UE could re-establish the RLC entity corresponding to the RB for the first cell, as shown in step 830.

In one embodiment, there could be two separate MAC (Medium Access Control) entities in the UE to support the first eNB and the second eNB. In addition, the RB could be used to transmit U-plane data. Furthermore, one or both of the RLC entities could be configured with an Acknowledged Mode (AM). In another embodiment, the PDCP packets could be PDCP SDUs and/or PDUs.

Referring back to FIGS. 3 and 4, in one embodiment, the device 300 could include a program code 312 stored in memory 310 for removing serving cells in a wireless communication system. In this embodiment, the device 300 operates in a scenario where (i) the UE is served by a first cell controlled by a first eNB, (ii) the UE is configured with a second cell controlled by a second eNB, and (iii) the UE is configured with a RB, wherein there is a PDCP entity corresponding to the RB and there are two RLC entities corresponding to the RB, the first RLC entity is for data transfer via the first cell and the second RLC entity is for data transfer via the second cell.

The CPU 308 could execute the program code 312 to enable the UE to transmit a PDCP status report to the first eNB, in response to reception of an instruction to remove the second cell, to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB. In one embodiment, the CPU 308 could further execute the program code 312 to enable the UE to deliver out-of-sequence RLC SDUs reassembled by the RLC entity corresponding to the first cell to the PDCP entity. In another embodiment, the CPU 308 could execute the program code 312 to enable the UE to re-establish the RLC entity corresponding to the RB for the first cell. In addition, the CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.

FIG. 9 is a flow chart 900 from the perspective of an eNB in accordance with one exemplary embodiment. The eNB operates in a configuration in which a UE is served by a first cell controlled by a first eNB. In step 905, the first eNB configures a second cell controlled by a second eNB to the UE.

In step 910, the first eNB configures a RB to the UE, wherein there is a PDCP entity corresponding to the RB in the first eNB and there are two RLC entities corresponding to the RB, one in the first eNB and the other in the second cell eNB. In one embodiment, the RB could be used to transmit U-plane data. Furthermore, one or both of the RLC entities could be configured with an Acknowledged Mode (AM).

In step 915, the first eNB transmits a RRC (Radio Resource Control) message to the UE to remove the second cell. In one embodiment, the RRC message could be a RRC Connection Reconfiguration message.

In step 920, the first eNB receives a PDCP status report from the UE, wherein the PDCP status report is transmitted by the UE in response to a removal of the second cell to indicate which PDCP packets of the RB need to be retransmitted. In one embodiment, the PDCP packets could be PDCP SDUs and/or PDUs.

In one embodiment, as shown in step 925, the first eNB retransmits the PDCP packets indicated in the PDCP status report.

Referring back to FIGS. 3 and 4, in one embodiment, the device 300 could include a program code 312 stored in memory 310 for removing serving cells in a wireless communication system, wherein a UE is served by a first cell controlled by a first eNB. The CPU 308 could execute the program code 312 to enable the first eNB (i) to configure a second cell controlled by a second eNB to the UE, (ii) to configure a RB to the UE, wherein there is a PDCP entity corresponding to the RB in the first eNB and there are two RLC entities corresponding to the RB, one in the first eNB and the other in the second cell eNB, (iii) to transmit a RRC (Radio Resource Control) message to the UE to remove the second cell, and (iv) to receive a PDCP status report from the UE, wherein the PDCP status report is transmitted by the UE in response to a removal of the second cell to indicate which PDCP packets of the RB need to be retransmitted.

In one embodiment, the CPU 308 could further execute the program code 312 to enable the first eNB to retransmit the PDCP packets indicated in the PDCP status report. In addition, the CPU 308 could execute the program code 312 to perform all of the above-described actions and steps or others described herein.

Various aspects of the disclosure have been described above. It should be apparent that the teachings herein may be embodied in a wide variety of forms and that any specific structure, function, or both being disclosed herein is merely representative. Based on the teachings herein one skilled in the art should appreciate that an aspect disclosed herein may be implemented independently of any other aspects and that two or more of these aspects may be combined in various ways. For example, an apparatus may be implemented or a method may be practiced using any number of the aspects set forth herein. In addition, such an apparatus may be implemented or such a method may be practiced using other structure, functionality, or structure and functionality in addition to or other than one or more of the aspects set forth herein. As an example of some of the above concepts, in some aspects concurrent channels may be established based on pulse repetition frequencies. In some aspects concurrent channels may be established based on pulse position or offsets. In some aspects concurrent channels may be established based on time hopping sequences. In some aspects concurrent channels may be established based on pulse repetition frequencies, pulse positions or offsets, and time hopping sequences.

Those of skill in the art would understand that information and signals may be represented using any of a variety of different technologies and techniques. For example, data, instructions, commands, information, signals, bits, symbols, and chips that may be referenced throughout the above description may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or particles, or any combination thereof.

Those of skill would further appreciate that the various illustrative logical blocks, modules, processors, means, circuits, and algorithm steps described in connection with the aspects disclosed herein may be implemented as electronic hardware (e.g., a digital implementation, an analog implementation, or a combination of the two, which may be designed using source coding or some other technique), various forms of program or design code incorporating instructions (which may be referred to herein, for convenience, as “software” or a “software module”), or combinations of both. To clearly illustrate this interchangeability of hardware and software, various illustrative components, blocks, modules, circuits, and steps have been described above generally in terms of their functionality. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the overall system. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present disclosure.

In addition, the various illustrative logical blocks, modules, and circuits described in connection with the aspects disclosed herein may be implemented within or performed by an integrated circuit (“IC”), an access terminal, or an access point. The IC may comprise a general purpose processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA) or other programmable logic device, discrete gate or transistor logic, discrete hardware components, electrical components, optical components, mechanical components, or any combination thereof designed to perform the functions described herein, and may execute codes or instructions that reside within the IC, outside of the IC, or both. A general purpose processor may be a microprocessor, but in the alternative, the processor may be any conventional processor, controller, microcontroller, or state machine. A processor may also be implemented as a combination of computing devices, e.g., a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration.

It is understood that any specific order or hierarchy of steps in any disclosed process is an example of a sample approach. Based upon design preferences, it is understood that the specific order or hierarchy of steps in the processes may be rearranged while remaining within the scope of the present disclosure. The accompanying method claims present elements of the various steps in a sample order, and are not meant to be limited to the specific order or hierarchy presented.

The steps of a method or algorithm described in connection with the aspects disclosed herein may be embodied directly in hardware, in a software module executed by a processor, or in a combination of the two. A software module (e.g., including executable instructions and related data) and other data may reside in a data memory such as RAM memory, flash memory, ROM memory, EPROM memory, EEPROM memory, registers, a hard disk, a removable disk, a CD-ROM, or any other form of computer-readable storage medium known in the art. A sample storage medium may be coupled to a machine such as, for example, a computer/processor (which may be referred to herein, for convenience, as a “processor”) such the processor can read information (e.g., code) from and write information to the storage medium. A sample storage medium may be integral to the processor. The processor and the storage medium may reside in an ASIC. The ASIC may reside in user equipment. In the alternative, the processor and the storage medium may reside as discrete components in user equipment. Moreover, in some aspects any suitable computer-program product may comprise a computer-readable medium comprising codes relating to one or more of the aspects of the disclosure. In some aspects a computer program product may comprise packaging materials.

While the invention has been described in connection with various aspects, it will be understood that the invention is capable of further modifications. This application is intended to cover any variations, uses or adaptation of the invention following, in general, the principles of the invention, and including such departures from the present disclosure as come within the known and customary practice within the art to which the invention pertains. 

What is claimed is:
 1. A method for removing a serving cell in a wireless communication system, comprising: a UE (User Equipment) is served by a first cell controlled by a first eNB (evolved Node B); the UE is configured with a second cell controlled by a second eNB; the UE is configured with a radio bearer (RB), wherein there is a PDCP (Packet Data Convergence Protocol) entity corresponding to the RB and there are two RLC (Radio Link Control) entities corresponding to the RB, one RLC entity for data transfer via the first cell and the other RLC entity for data transfer via the second cell; and the UE delivers out-of-sequence RLC SDUs (Service Data Units) reassembled by the RLC entity corresponding to the first cell to the PDCP entity in response to reception of an instruction to remove the second cell.
 2. The method of claim 1, further comprising: the UE transmits a PDCP status report to the first eNB to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB.
 3. The method of claim 1, further comprising: the UE re-establishes the RLC entity corresponding to the RB for the first cell.
 4. The method of claim 1, wherein there are two separate MAC (Medium Access Control) entities in the UE to support the first eNB and the second eNB.
 5. The method of claim 1, wherein the RB is used for U-plane data transmission.
 6. The method of claim 1, wherein the RLC entity is configured with an Acknowledged Mode (AM).
 7. The method of claim 2, wherein the PDCP packets are PDCP SDUs or PDCP PDUs.
 8. A method for removing a serving cell in a wireless communication system, comprising: a UE (User Equipment) is served by a first cell controlled by a first eNB (evolved Node B); the UE is configured with a second cell controlled by a second eNB; the UE is configured with a radio bearer (RB), wherein there is a PDCP (Packet Data Convergence Protocol) entity corresponding to the RB and there are two RLC (Radio Link Control) entities corresponding to the RB, one RLC entity for data transfer via the first cell and the other RLC entity for data transfer via the second cell; and the UE transmits a PDCP status report to the first eNB, in response to reception of an instruction to remove the second cell, to indicate which PDCP packets of the RB need to be retransmitted if the PDCP status report is configured as required to the RB.
 9. The method of claim 8, further comprising: the UE delivers out-of-sequence RLC SDUs (Service Data Units) reassembled by the RLC entity corresponding to the first cell to the PDCP entity.
 10. The method of claim 8, further comprising: the UE re-establishes the RLC entity corresponding to the RB for the first cell.
 11. The method of claim 8, wherein there are two separate MAC (Medium Access Control) entities in the UE to support the first eNB and the second eNB.
 12. The method of claim 8, wherein the RB is used for U-plane data transmission.
 13. The method of claim 8, wherein the RLC entity is configured with an Acknowledged Mode (AM).
 14. The method of claim 8, wherein the PDCP packets are PDCP SDUs or PDCP PDUs.
 15. A method for removing a serving cell in a wireless communication system, wherein a UE (User Equipment) is served by a first cell controlled by a first eNB (evolved Node B), comprising: the first eNB configures a second cell controlled by a second eNB to the UE; the first eNB configures a radio bearer (RB) to the UE, wherein there is a PDCP (Packet Data Convergence Protocol) entity corresponding to the RB in the first eNB and there are two RLC entities corresponding to the RB, one in the first eNB and the other in the second cell eNB; the first eNB transmits a RRC (Radio Resource Control) message to the UE to remove the second cell; and the first eNB receives a PDCP status report from the UE, wherein the PDCP status report is transmitted by the UE in response to a removal of the second cell to indicate which PDCP packets of the RB need to be retransmitted.
 16. The method of claim 15, further comprising: the first eNB retransmits the PDCP packets indicated in the PDCP status report.
 17. The method of claim 15, wherein the RB is used for U-plane data transmission.
 18. The method of claim 15, wherein the RLC entity is configured with an Acknowledged Mode (AM).
 19. The method of claim 15, wherein the PDCP packets are PDCP SDUs or PDCP PDUs.
 20. The method of claim 15, wherein the RRC message is a RRC Connection Reconfiguration message. 